it should not replace the volumes, right?

No, just everything on root disk (ssh keys, etc.)

Oh there is no playbook for it, that was the point right?
Love the branch name btw :D

Please do not merge this. My changes need to be merged 1st. I will manually roll out this this evening and update you later. Converting this to a draft for now.

Oh there is no playbook for it, that was the point right?

yeah there has never been a playbook for it, maybe one can be written now, but at minimum we can install it via system packages which will be more reliable than dokku-in-docker.

Love the branch name btw :D

tailscale approved :p

I rolled it out and then realized that many of our VMs, which were deployed with the regular cloud flavors, are currently not working due to this issue and unfortunately now this VM is also not reachable due to the same. I will update you as soon as the VM is online. However, a new VM has been spawned with Ubuntu 22.04 and the volume that was previously attached is also made available,

resource "openstack_compute_volume_attach_v2" "dokku-va" {
  instance_id = openstack_compute_instance_v2.dokku.id
  volume_id   = "6cbce9f7-1ffd-4848-9ec8-0a2ccfd52225"
  device      = "/dev/vdb"
}

I will close this PR and push my changes to my PR along with the state file updates.

Change commit: 589cc31

@hexylena, your VM is up and running. The username is ubuntu. Please send me your SSH key so I can add it to the VM directly, or I can recreate the VM with a cloud-init this time and add your key to the TF file itself.